-
-
Notifications
You must be signed in to change notification settings - Fork 3.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Async channel v2 #10692
Async channel v2 #10692
Conversation
@@ -13,6 +13,7 @@ pub mod extract_resource; | |||
pub mod globals; | |||
pub mod gpu_component_array_buffer; | |||
pub mod mesh; | |||
#[cfg(not(target_arch = "wasm32"))] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason why the entire module is hidden on wasm32? Otherwise we need to document this or this might be a sharp API edge.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pipelined rendering plugin already doesn't work on wasm32. So I don't think removing it is a significant change. Though I agree that it should be documented.
It looks like your PR is a breaking change, but you didn't provide a migration guide. Could you add some context on what users should update when this change get released in a new version of Bevy? |
0b16d51
to
f055da2
Compare
Btw should this not be just |
It was to match futures-lite versions. |
Objective
Solution
send_blocking
on wasm anymore. So don't compile the pipelined rendering plugin on wasm anymore.Migration Guide
PipelinedRendering
plugin is no longer exported on wasm. If you are including it in your wasm builds you should remove it.